SNX is the "SPARCS-N4 eXchange" system for importing your live legacy system data prior to going live with N4. You can import SNX documents into N4 either by using the SNX Importer form or through the Java Messaging Service (JMS) (by sending messages to N4 through preconfigured JMS queues). These instructions describe how to use the SNX Importer form for data conversion. See your Navis representative for information about how to import SNX documents via JMS.
Before you can implement the SNX import, you must have already loaded the initial reference data and set up a basic topology (see the Navis N4: Installation Guide for Windows or the Navis N4: Installation Guide for Linux for instructions). These steps are necessary because topology, equipment types, and UNLOC codes must be present in N4 for a successful data import. Line operators should be present in N4 as well, but if they are missing, N4 creates a stub record.
The SNX Importer form imports data into N4 from an import data XML file using the snx.xsd schema file. Your Navis representative provides you with the latest version of the SNX schema file.
For data conversion, you must export data from your legacy system and create an import data XML file that contains two types of data entities:
Reference data: Entities on which the units depend but which are usually set up once and not updated again. (For example, routing points.)
Working data: The principle operational entities of the system, such as units, vessel visits, and bookings. These entities have a time-limited life cycle.
In addition, when importing some entities, N4 creates other stub records with the primary key (gkey) information only. For example, if you import units and include a group code, N4 also creates the group code with just the group ID; it does not have any descriptive attributes. N4 specifies all of the supported entities and attributes in the snx.xsd schema file.
If you are using EDI to integrate another system with N4, such as an in-house system, you can use the SNX Importer form to quickly test sample inbound EDI files. For more information, see Importing EDI files using SNX (on page 1).
To implement the SNX import:
Create an import data XML file.
You can expect the process of creating the import data XML file for the SNX import to take several days or weeks, depending on the scope and condition of the source data.
Import data (on page 1).
When the successful import is complete, the module for which you imported data displays the data. For example, if you imported a compiled yard file with SNX, the data displays as a new yard model in the Yard Models view (on page 1).
If there are errors, fix the data with errors and re-import data (on page 1).
See also Update data with an SNX import (on page 1).